Skip to content

Update meson build requirement #952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 24, 2019
Merged

Update meson build requirement #952

merged 1 commit into from
Jun 24, 2019

Conversation

baylesj
Copy link
Contributor

@baylesj baylesj commented Jun 24, 2019

Currently, we have a build type warning due to listing a requirement for
meson build version that doesn't implement features we use in our build
file. The minimum meson build version required is actually 0.50.0, so
this PR updates our meson.build file to depend on 0.50.0.

Currently, we have a build type warning due to listing a requirement for
meson build version that doesn't implement features we use in our build
file. The minimum meson build version required is actually 0.50.0, so
this PR updates our meson.build file to depend on 0.50.0.
@baylesj baylesj merged commit 6935317 into open-source-parsers:master Jun 24, 2019
@baylesj baylesj deleted the update-meson-req branch June 24, 2019 21:08
@baylesj
Copy link
Contributor Author

baylesj commented Jun 25, 2019

Fixes #917

@cdunn2001
Copy link
Contributor

We still need directions on how to build with Meson. All the cmake support is user-provided, not official. We actually use meson in TravisCI.

I'll add a PR for Meson directions, plus Meson updates ...

@cdunn2001
Copy link
Contributor

Hmmm. I don't actually see a merge commit for the README changes. Well, that's what I meant to comment on...

@cdunn2001
Copy link
Contributor

Oh, I see. That comment was moved to CONTRIBUTING.md. Ok.

I just updated Meson in my Homebrew, which took some time. Apparently we no longer support older Meson at all, which is fine...

@cdunn2001
Copy link
Contributor

I was getting this:

    DEPRECATION: Project targetting '>= 0.41.1' but tried to use feature depreca
    Build targets in project: 3
    WARNING: Deprecated features used:
     * 0.48.0: {'python3 module'}

So I did this:

-python = import('python3').find_python()
+python = find_program('python3', 'python')

But I no longer see that deprecation warning either way. Strange. It does seem to be deprecated:

This module is deprecated and replaced by the python module.

@cdunn2001 cdunn2001 mentioned this pull request Nov 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants